Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

2092

reference
59-tree-1
name
2092
tree-preservation-order

undefined

59-tpo-1
uprn
address-text
point
POINT (-0.999472 50.793095)
geometry
MULTIPOLYGON (((-0.999415 50.793089,-0.999418 50.793101,-0.999426 50.793111,-0.999438 50.793119,-0.999454 50.793124,-0.999471 50.793126,-0.999489 50.793124,-0.999505 50.793119,-0.999518 50.793111,-0.999526 50.793101,-0.999529 50.793090,-0.999526 50.793079,-0.999518 50.793069,-0.999506 50.793061,-0.999490 50.793056,-0.999473 50.793054,-0.999455 50.793056,-0.999439 50.793060,-0.999427 50.793068,-0.999418 50.793078,-0.999415 50.793089)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL